Skip to content

Podcast feed generator episode image feature#119

Open
Goosse wants to merge 12 commits into
JohnSundell:masterfrom
Goosse:podcast-generator-episode-image-feature
Open

Podcast feed generator episode image feature#119
Goosse wants to merge 12 commits into
JohnSundell:masterfrom
Goosse:podcast-generator-episode-image-feature

Conversation

@Goosse

@Goosse Goosse commented Dec 18, 2021

Copy link
Copy Markdown
Contributor

This pull request adds the functionality of using an item's imagePath to include an image unique to that episode in the RSS feed.

@JohnSundell JohnSundell left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, thanks a lot @Goosse (and sorry for taking so long to provide any feedback on this!). I just made a few stylistic changes to the code, and will merge once CI passes 👍

@JohnSundell

Copy link
Copy Markdown
Owner

@Goosse Could you perhaps merge the latest master into this PR branch, to see if that fixes the CI issues?

@Goosse

Goosse commented Apr 24, 2022

Copy link
Copy Markdown
Contributor Author

Looks like the merge fixed the CI issues

.explicit(metadata?.isExplicit ?? false),
.duration(audioDuration),
.image(config.imageURL),
.image(imageURL ?? config.imageURL),

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't it be better to exclude the image tag altogether when the item has no specific image?

As far as I've been able to tell, all clients will fall back to the main <itunes:image> at the channel level when the episode has no custom artwork. For shows with lots of episodes, having these duplicate tags in the feed add up and make the feed larger than it needs to be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants